澳大利亚专利AU2013224641A1 System and method of loading a transaction card and processing repayment on a mobile device

专利PDF首页>>澳大利亚专利

专利附录

专利说明

权利要求

类似技术

同族专利

引用文献

法律状态

优先权

专利摘要:
The embodiments described herein provide in one aspect, a method of loading a transaction card account onto a mobile device, the mobile device comprising a memory and a contactless reader, the method comprising: reading, via the contactless reader, transaction card information from a physical contactless transaction card corresponding to the transaction card account; sending a retrieval message, to an issuer server, to retrieve a card security credential for the transaction card account, the retrieval message comprising the transaction card information for identifying the transaction card account at the issuer server; receiving, from the issuer server, a card security credential for the transaction card account; and storing, the transaction card information and the card security credential as a transaction card corresponding to the transaction account, on the memory of the mobile device.
公开号:AU2013224641A1
申请号:U2013224641
申请日:2013-02-22
公开日:2014-09-18
发明作者:Michael FAINSHTEIN；Mikhail KUSHEVSKY；Valdis Andris MARTINSONS
申请人:XRomb Inc；
IPC主号:G06Q20-32

专利说明:
WO 2013/123577 PCT/CA2013/000151 Title: System and Method of Loading a Transaction Card and Processing Repayment on a Mobile Device Cross-Reference to Related Applications 5 [1] This application claims the benefit of: United States Provisional Patent Application No. 61/602,421, entitled "System and Method of Loading a Transaction Card and Processing Repayment on a Mobile Device", filed February 23, 2012; and United States Patent Application No. 13/464,484, entitled "System and Method of Loading a Transaction Card and Processing Repayment on a Mobile Device", filed 10 May 4, 2012. The entire contents of United States Provisional Patent Application No. 61/602,421 and United States Patent Application No. 13/464,484 are hereby incorporated by reference. Field 15 [2] The described embodiments relate to a system and method of loading a transaction card and processing repayment on a mobile device. Background [3] Physical plastic transaction cards (e.g., a payment card such as a debit card or a Visa* credit card) may contain embedded contactless communications 20 technology within the card to enable transmission of transaction card information to a contactless reader at a point-of-sale terminal. Such technology may include specialized integrated circuits (ICs) and antennas that communicate, for example, using the Near Field Communications (NFC) standard. [4] Modern mobile devices have also started to incorporate such contactless 25 communications technology. Software applications executing on these mobile devices may be configured to use the contactless technology embedded in the mobile devices to enable the mobile device to function as a transaction card. [5] To avoid having to carry both a mobile device and physical transaction cards, users may desire to load their existing transaction cards onto their mobile device. 30 [6] Existing methods of loading such existing plastic transaction cards are inefficient and error-prone as they require the manual entry of the transaction card information (e.g., credit card number and expiry date) onto the mobile device. - 1 - WO 2013/123577 PCT/CA2013/000151 [7] There is thus a need for improved systems and methods of loading a transaction card onto a mobile device. [8] After the transaction card is loaded onto the mobile device, the mobile device may be configured for conducting mobile payment transactions, such as peer-to 5 peer transactions. Certain peer-to-peer payments, such as "I Owe You"s (IOUs), can be difficult to enforce due to their informal nature. Furthermore, the party owing the IOU may not remember to repay the IOU even if that party has available funding. [9] There is, thus, also a need for ensuring automatic repayment of IOUs as soon as repayment funds are available. 10 Summary [10] In a first aspect, some embodiments of the invention provide a method of loading a transaction card account onto a mobile device, the mobile device comprising a memory and a contactless reader, the method comprising: 15 - reading, via the contactless reader, transaction card information from a physical contactless transaction card corresponding to the transaction card account; - sending a retrieval message, to an issuer server, to retrieve a card security credential for the transaction card account, the retrieval 20 message comprising the transaction card information for identifying the transaction card account at the issuer server; - receiving, from the issuer server, a card security credential for the transaction card account; and - storing, 25 - the transaction card information, and - the card security credential as a transaction card corresponding to the transaction account, on the memory of the mobile device. [11] In a second aspect, some embodiments of the invention provide a system for 30 loading a transaction card, the system comprising: - a mobile device comprising a processor, a contactless reader operatively coupled to the processor, and a memory storing a plurality -2- WO 2013/123577 PCT/CA2013/000151 of instructions, which when executed by the processor causes the processor to: - read, via the contactless reader, transaction card information from a physical contactless transaction card corresponding to 5 the transaction card account; - send a retrieval message, to an issuer server, to retrieve a card security credential for the transaction card account, the retrieval message comprising the transaction card information for identifying the transaction card account at the issuer server; 10 - receive, from the issuer server, a card security credential for the transaction card account; and - store, - the transaction card information, and - the card security credential 15 as a transaction card corresponding to the transaction account, on the memory of the mobile device. [12] In a third aspect, some embodiments of the invention provide a method of processing an amount owing from a first transaction account to a second transaction account, the method comprising 20 - providing a first mobile device comprising a first memory storing a first transaction card corresponding to the first transaction account; - providing a second mobile device comprising a second memory storing a second transaction card corresponding to the second transaction account; 25 - receiving at the second mobile device, from the first mobile device, an acknowledgement that acknowledges the amount owing; - transmitting, from the second mobile device to the first mobile device, an account identifier corresponding to the second transaction account; and 30 - receiving, at the first mobile device, a load amount to be loaded to the first transaction account, wherein, prior to adding the load amount to the first transaction account, the first mobile device is configured to use - 3 - WO 2013/123577 PCT/CA2013/000151 the load amount to repay the amount owing to the second transaction account. [13] In a fourth aspect, some embodiments of the invention provide a system for processing an amount owing from a first transaction account to a second transaction 5 account, the system comprising - a first mobile device comprising a first processor and a first memory storing a first transaction card corresponding to the first transaction account; - a second mobile device comprising a second processor and a second 10 memory storing a second transaction card corresponding to the second transaction account, wherein the second processor is configured to: - receive, from the first mobile device, an acknowledgement that acknowledges the amount owing; and 15 - transmit, to the first mobile device, an account identifier corresponding to the second transaction account; and - wherein, the first mobile device configured to: - receive a load amount to be loaded to the first transaction account, and, prior to adding the load amount to the first 20 transaction account, the first mobile device is configured to use the load amount to repay the amount owing to the second transaction account. Brief Description of the Drawings 25 [14] A preferred embodiment of the present invention will now be described in detail with reference to the drawings, in which: Figure 1 is a block diagram of a system for loading a transaction card and processing repayment on a mobile device, in accordance with an embodiment of the present disclosure; 30 Figure 2 is a block diagram of a mobile device, in accordance with an embodiment of the present disclosure; - 4- WO 2013/123577 PCT/CA2013/000151 Figure 3 is a flowchart diagram illustrating the steps of loading a transaction card onto a mobile device, in accordance with an embodiment of the present disclosure; Figure 4 is an illustration of an example screenshot of a mobile device when 5 preparing to load a transaction card onto the mobile device, in accordance with an embodiment of the present disclosure; Figure 5 is an illustration of an example screenshot of a mobile device after transaction card information has been read from a contactless transaction card, in accordance with an embodiment of the present disclosure; 10 Figure 6 is an illustration of an example security input screen on a mobile device that may be shown after the screenshot of Figure 5; Figure 7 is an illustration of an example transaction card selection screen after a transaction card has been loaded onto a mobile device; Figure 8 is a flowchart diagram illustrating the steps of processing repayment 15 for an amount owing, in accordance with an embodiment of the present disclosure; Figure 9 is a diagram illustrating the creating and receiving of an acknowledgement that acknowledges an amount owing, in accordance with an embodiment of the present disclosure; Figure 10 is an example screenshot on a mobile device after receiving a load 20 amount, in accordance with an embodiment of the present disclosure; Figure 11 is an example screenshot of a payment received notification, in accordance with an embodiment of the present disclosure; Figure 12 is an example screenshot of an account balance screenshot after the amount owing is repaid, that may be shown after the screenshot in Figure 10, in 25 accordance with an embodiment of the present disclosure; Figure 13 is an example screenshot of a payment queue, in accordance with an embodiment of the present disclosure; and Figure 14 is an example user interface for selecting options associated with the amount owing. 30 Description of Exemplary Embodiments [15] It will be appreciated that numerous specific details are set forth in order to provide a thorough understanding of the example embodiments described herein. -5- WO 2013/123577 PCT/CA2013/000151 However, it will be understood by those of ordinary skill in the art that the embodiments described herein may be practiced without these specific details. In other instances, well-known methods, procedures and components have not been described in detail so as not to obscure the embodiments described herein. 5 Furthermore, this description and the drawings are not to be considered as limiting the scope of the embodiments described herein in any way, but rather as merely describing the implementation of the various embodiments described herein. [16] The embodiments of the systems and methods described herein may be implemented in hardware or software, or a combination of both. However, 10 preferably, these embodiments are implemented in computer programs executing on programmable computers each comprising at least one processor (e.g., a microprocessor), a data storage system (including volatile and non-volatile memory and/or storage elements), at least one input device, and at least one output device. For example and without limitation, the programmable computers (referred to below 15 as computing devices) may be a personal computer, laptop, personal data assistant, cellular telephone, smart-phone device, tablet computer, and/or wireless device. Program code is applied to input data to perform the functions described herein and generate output information. The output information is applied to one or more output devices, in known fashion. 20 [17] Each program is preferably implemented in a high level procedural or object oriented programming and/or scripting language to communicate with a computer system. However, the programs can be implemented in assembly or machine language, if desired. In any case, the language may be a compiled or interpreted language. Each such computer program is preferably stored on a storage media or a 25 device (e.g. ROM or magnetic diskette) readable by a general or special purpose programmable computer, for configuring and operating the computer when the storage media or device is read by the computer to perform the procedures described herein. The subject system may also be considered to be implemented as a computer-readable storage medium, configured with a computer program, where 30 the storage medium so configured causes a computer to operate in a specific and predefined manner to perform the functions described herein. [18] Furthermore, the system, processes and methods of the described embodiments are capable of being distributed in a computer program product -6- WO 2013/123577 PCT/CA2013/000151 comprising a computer readable medium that bears computer usable instructions for one or more processors. The medium may be provided in various forms, including one or more diskettes, compact disks, tapes, chips, wireline transmissions, satellite transmissions, internet transmission or downloadings, magnetic and electronic 5 storage media, digital and analog signals, and the like. The computer useable instructions may also be in various forms, including compiled and non-compiled code. [19] Reference is first made to Figure 1, shown there is a block diagram illustrating a system for loading a transaction account and processing repayment on a mobile 10 device, referred to generally as 100. The system may include one or more mobile devices 140, and an e-wallet server 120, each including a network interface (not shown) for connecting to a network 104. The mobile device 140 may interact with one or more transaction cards 150 via contactless communication standards such as NFC. When loading a transaction card onto the mobile device 140, the mobile 15 device 140 may be configured to communicate with issuer server 110 to download to the mobile device 140, a card security credential corresponding to the transaction cards 150. [20] From a high-level perspective, some embodiments described herein are generally directed to a system of loading a transaction card account corresponding 20 to the transaction card 150 onto a mobile device 140. To do so, the mobile device 140 may be configured to operate a contactless reader embedded within a mobile device 140 to read transaction card information from an existing contactless transaction card 150 to be loaded. Such reading of transaction card information for the purpose of loading onto the mobile device 140 may reduce the likelihood of error 25 over methods of manually entering the transaction card information onto the mobile device 140. Also, employing the contactless reader to read the transaction card information may speed up the process of loading a transaction account onto a mobile device 140. [21] The various components in Figure 1 will now be described in greater detail. 30 [22] Issuer server 110 may include a server from an organization that issues a transaction card. Transaction cards may, for example include payment cards (such as credit cards or debit cards), loyalty rewards card, gift cards, or identification cards. For a credit card (e.g., Visa* or MasterCard®), the issuer server 110 may be a server -7- WO 2013/123577 PCT/CA2013/000151 from the issuer of the credit card. The issuer server 110 may store various data items relating to the transaction account corresponding to the transaction card. Such data items may include a card security credential for the transaction account that may be transmitted to the mobile device 140 as a part of the loading of the 5 transaction card onto the mobile device 140. [23] Electronic wallet server 120 may store account information related to an electronic wallet (referred to herein as an "e-wallet") application executable on a mobile device 140. For example, such information may include a login username and/or password for an e-wallet account, and/or any transaction accounts 10 associated with the e-wallet account. Such data may be stored in the e-wallet database 122. [24] In some embodiments, the e-wallet application may be configured to perform various operations performed by the mobile device 140 described herein. [25] A mobile device 140 may be any computing device that includes a 15 contactless reader (e.g., an NFC chip) operable to read transaction card information from a contactless transaction card. Such devices 110 may include cellular phones, smartphones (e.g., Apple* iPhone*, BlackBerry*, Android TM or other suitable network-connected computing devices such as a tablet computer (e.g., Apple* iPad TM) with contactless readers embedded therein. In some embodiments, the 20 mobile device 140 may include a secure element for storing the transaction card. [26] The network 104 may be any network(s) capable of carrying data including the Internet, Ethernet, plain old telephone service (POTS) line, public switch telephone network (PSTN), integrated services digital network (ISDN), digital subscriber line (DSL), coaxial cable, fiber optics, satellite, mobile, wireless (e.g. Wi 25 Fi, WiMAX), SS7 signaling network, fixed line, local area network, wide area network, and others, including any combination of these. [27] Referring to Figure 2, therein illustrated is a block diagram of a mobile device 140, shown in greater detail. The mobile device 140 may include a processor 210 that is operatively connected to a communication module 220, a display 230, a 30 contactless transceiver 240 (which may include contactless reader functionality), and a memory 250. [28] The communication module 220 may be operated by the processor 110 to enable communication between the mobile device 140 and the issuer server 110. -8- WO 2013/123577 PCT/CA2013/000151 The communication module 220 may include various communication components (e.g., dedicated or integrated controllers and/or antennas) that communicate using known wireless communications technologies. For example, the communications module 220 may be configured to operate on one or more of the following 5 standards: Global System for Mobile Communications (GSM), General Packet Radio Service (GPRS), High Speed Packet Access (HSPA), and Long Term Evolution (LTE). Additionally or alternatively, the mobile device may include other components for enabling the apparatus to communicate via other communications standards such as WiFi or Bluetooth. 10 [29] The display 230 may be operable by the processor 210 to display a user interface for interacting with a user. Various example user interface screenshots are illustrated and discussed below. [30] The contactless transceiver 240 may enable the mobile device 140 to both transmit and receive (e.g., read) data using contactless communications with a 15 contactless element. That is, the transceiver 240 may operate as both a contactless transmitter and a reader. In some embodiments, the contactless transceiver 240 may be only a reader. [31] The contactless receiver 240 may operate on the Near Field Communication (NFC) standard, or a NFC reader. The NFC standard employs radio frequency 20 identification (RFID) technology that uses radio frequency electromagnetic fields to transfer data. NFC is a particular type of RFID technology that is configured to only allow contactless communications when the contactless reader is within close proximity to the contactless element (which may also be configured to employ the NFC standard). The use of NFC may enhance security by reducing the likelihood 25 that data stored on the contactless element would be read by contactless readers that are further than the required distance away. Generally, the NFC standard enables bidirectional communication between at least two devices. The NFC standard may include the ISO/IEC 18092 standard and other telecommunication standards defined by the European Telecommunications Standards Institute (ETSI). 30 [32] The contactless element may include an embedded integrated circuit that enables wireless contactless communication with the contactless reader 132 (e.g., a NFC chip that enables communications via the NFC standard). Through the wireless communication, the contactless element may provide the transaction card -9- WO 2013/123577 PCT/CA2013/000151 information associated with a transaction account to the contactless reader 132. Transaction card information may include any type of information that is made available via the contactless element of the contactless transaction card. This may include card identification numbers, card balances, and the like. For example, in the 5 scenario where the transaction card is a contactless credit card, the transaction card information may include the name of the cardholder, an identifier associated with the transaction account (e.g., a credit card number), an expiry date of the transaction account, and/or a card verification value (CVV). [33] As noted, the memory 250 may store an e-wallet application that is 10 executable by the processor 210 to configure the contactless transceiver 240 to read the transaction card information from a contactless transaction card 150. In various embodiments, the memory 250 of the mobile device may include different components: a main memory space for the storage of applications, and a separate secure memory space that is only accessible by trusted applications. 15 [34] In some embodiments, the separate secure memory space may be a secure element. A secure element is a protected processor and memory space of a mobile device 140 that is separate and independent of the main processor and memory space of the mobile device 140. That is, the secure element (secure memory and execution environment) may be an environment in which application code and 20 application data can be securely stored and administered and in which secure execution of applications occur. The secure element may be embodied in highly secure cryptographic chips (e.g., a smart card chip). [35] Only trusted applications such as an e-wallet application may access the secure element to store data onto it. The secure element may provide delimited 25 memory for each application and functions that encrypt, decrypt, and sign data packets being communicated to and from the secure element. This may increase the security of the secure element and reduce the possibility that the secure element may be tampered with. [36] In some embodiments, the e-wallet application may be executing on the 30 secure execution environment of the secure element. [37] The secure element may be provided in various ways on the mobile device 140. For example, the secure element may be coupled with the NFC chip on an integrated integrated circuit, or it may be provided on a Subscriber Identity Module -10- WO 2013/123577 PCT/CA2013/000151 (SIM) card of the mobile device 140, or it may be provided on a removable memory (e.g., microSD) integrated circuit that may be entered into a slot for receiving such memory on the mobile device 140. It will be understood that other methods of providing a secure element on the mobile device 140 may be possible. 5 [38] Referring to Figure 3, shown is a flowchart diagram illustrating the steps of a method of loading a transaction card onto a mobile device, shown generally as 300. To illustrate the steps of the method, reference will be made simultaneously to Figures 4, 5, 6 and 7 which illustrate various example screenshots of a mobile device 140 for an example scenario in which an owner of Visa* credit card, "John 10 Smith", adds his credit card to his mobile device 140. [39] At 310, the mobile device 140 may read, via the contactless reader, transaction card information from a physical contactless transaction card corresponding to the transaction card account. The contactless reader may comprise a Near Field Communications (NFC) integrated circuit (IC). 15 [40] As noted above, the contactless transceiver 240 of mobile device 140 may be operable to perform the operations of a contactless reader. However, it will be understood that a contactless transceiver 270 is not required and then a component that is only able to perform contactless reading functions (e.g., a contactless reader) may be sufficient. 20 [41] Referring simultaneously to Figure 4, shown there generally as 400 is an illustration of an example screenshot of a mobile device 140, when preparing to load a transaction card onto the mobile device, in accordance with an embodiment of the present disclosure. [42] In the example scenario, the physical plastic transaction card 150 25 corresponds to a Visa* credit card issued by an organization called "ABC Bank". Plastic transaction cards typically include various types of transaction card information on the surface of the card itself. Illustrated as a credit card, the transaction card 150 may include an identifier associated with the contactless transaction card 150 (e.g., as illustrated, a credit card number 150ba), a name 154a 30 of the owner of the credit card, and an expiry date for the credit card 156a. In order to conduct contactless transactions, the contactless transaction card 150 may house a contactless element 158 (which is shown in dotted outline because the contactless element may not be visually apparent from the exterior of the transaction card). The - 11 - WO 2013/123577 PCT/CA2013/000151 contactless transaction card 150 may also have a symbol 159 displayed on the surface of the card to indicate that it is enabled for contactless transactions. [43] When operating the e-wallet application stored on the mobile device 140, the e-wallet application may be configured to present a user interface 410 (entitled 5 "John's E-Wallet" in the example scenario) on the display 230 of the mobile device 140. One feature of the e-wallet application may be to enable the loading of a transaction account onto the mobile device 140. Such feature may allow a user to load either manually (i.e., by typing in the transaction card information onto the mobile device through an input mechanism on the mobile device), or by reading the 10 transaction card information from the contactless transaction card 150 via the contactless reader. If the mobile device 140 receives input selecting to load a transaction account by contactless means, the mobile device may be configured present a user interface 420 on the display 230 of the mobile device 140 to request the user to bring the physical plastic contactless card 150 corresponding to the 15 transaction account he/she wishes to load in close proximity to the mobile device 140. Such user interface 420 may include a cancel button 422 to allow a user to cancel the reading operation. [44] It will be understood that although illustrated in the context of an e-wallet application, an e-wallet application is not required to practice the subject 20 embodiments. For example, the operating system of the mobile device 140 may be configured to directly load the transaction account onto the mobile device 140, without the need of an e-wallet application. [45] The mobile device 140 may then activate the contactless reader to read the transaction card information from the contactless transaction card 150. 25 [46] Referring to Figure 5, therein illustrated is an example screenshot of a mobile device 140 after the transaction card information shown in Figure 4 has been read from a contactless transaction card 150. Similar to what is shown in Figure 4, the e wallet application executing on mobile device 140 may display a user interface 410 in the display 230 of the mobile device 140 that indicates that the transaction card 30 information has been successfully received. For example, this may be a message 510 showing "Received Card Information!" [47] The mobile device 140 may then display the transaction card information that has been read via the contactless reader. Displaying the transaction card -12- WO 2013/123577 PCT/CA2013/000151 information may allow the user to view and confirm the transaction card information before storing the transaction card onto the mobile device. In the illustrated example in which the owner of the mobile device 140 "John Smith" is loading his "ABC Bank Visa*" card onto his mobile device 140, the mobile device 140 may display the 5 various public details about the credit card on the display 230 of the mobile device 140. For example, the mobile device 140 may display the name of the cardholder 154b, the identifier associated with the transaction account (e.g., the credit card number 150bb), the expiry date for the transaction account 156b, and the card verification value (CVV) 520. 10 [48] The mobile device 140 may also present a "Save Now" button 512 to allow a user to confirm that the transaction card information that has been read via the contactless reader is correct, and that the user desires to continue with the transaction card loading process. [49] As noted, existing methods of manually entering the transaction card 15 information into the mobile device 140 may be slow and inaccurate. As such, it may be desirable to read the transaction card information via the contactless reader to improve the speed and accuracy at which the transaction card 150 can be loaded. [50] Also, existing methods of manually entering transaction card information may be unsecure as it may be possible for a nefarious person to obtain such information 20 (e.g., the name of the card holder, the credit card number, card expiry date and/or the CVV) by stealing it. By reading the transaction card information via the contactless transaction, the mobile device 140 may be able to confirm the presence of the physical plastic card when loading the transaction card onto the mobile device. As it is less likely for a contactless physical plastic card to be cloned than it 25 is simply for the transaction card information to stolen and reused, the subject embodiments may provide enhanced security over existing methods of manually entering the transaction card information onto the mobile device 140. [51] Storing the transaction card onto the mobile device 140 may not include just simply storing the transaction card information read from the contactless transaction 30 card 150. In various embodiments, the storing may also include storing a card security credential for the transaction card account. For example, the card security credential may be a shared secret (e.g., an encrypted Personal Identification -13- WO 2013/123577 PCT/CA2013/000151 Number (PIN)) that needs to be verified before the mobile device 140 can select the stored transaction account for use in a subsequent purchase transaction). [52] The card security credential may be retrieved from the issuer server 110. [53] At 320, the mobile device 140 may send a retrieval message, to an issuer 5 server 110, to retrieve a card security credential for the transaction card account, the retrieval message comprising the transaction card information for identifying the transaction card account at the issuer server 110. [54] As noted, the issuer server 110 may be a remote server of the issuing organization that issued the transaction card 150. To determine how to contact the 10 issuer server 110, the e-wallet application may be configured to communicate with the e-wallet server 120 to obtain addressing information (e.g., Internet Protocol (IP) addresses, port numbers, domain names, etc.) for the issuer server 110. In various embodiments, the e-wallet server 120 may store addressing information of issuer servers 110 associated with various types of well-known transaction cards (e.g., 15 major credit card companies, debit processing networks, etc.). [55] At 330, the mobile device 140 may receive, from the issuer server 110, a card security credential for the transaction card account. [56] In addition to storing the security credential on the mobile device 140, the mobile device 140 may be configured to use the security credential as an added 20 security feature. For example, the mobile device 140 may be configured to display a user interface on the mobile device 140 to receive a security input for verification against the card security credential. For example, the security input may be an inputted Personal Identification Number (PIN) and the card security credential may comprise an encrypted PIN. Such embodiments may enhance security by allowing 25 the authentication of the owner of the transaction account before allowing the storage of the transaction card onto the mobile device 140. [57] Referring to Figure 6, shown there is an illustration of an example security input screen of a user interface 410 of the e-wallet application, as configured to be shown on display 230 of the mobile device 140. Continuing with the example, the e 30 wallet application may, after requesting an encrypted PIN security credential for the "ABC Visa*" card from the issuer server 110, request the entry of a PIN security input for verification against the encrypted PIN that has been received. As illustrated, the security input screen may display a message 610 ("Enter PIN to -14- WO 2013/123577 PCT/CA2013/000151 Complete Loading") informing the user that a PIN needs to be entered and verified to complete the loading process, a keypad 614 for entering the PIN, and a text box 612 to provide feedback when a digit of the keypad 614 is selected. [58] After the security input has been entered, the mobile device 140 may verify 5 the security input against the received card security credential. For example, in the example scenario, this may involve determining whether the inputted PIN matches the encrypted PIN received from the issuer server 110. In embodiments where the security input does not match the card security credential, the mobile device 140 may display a message rejecting the security input. 10 [59] At 340, the mobile device 140 may store, on the memory of the mobile device 140, the transaction card information, and the card security credential as a transaction card corresponding to the transaction account. In embodiments where the security input is to be verified, the displaying of a user interface to receive a security input and the verifying of the security input against the card security 15 credential may be performed prior to the storing, with the storing only occurring if the security input is verified. [60] As the mobile device may be used as the contactless transaction card itself after being stored on the mobile device, the stored transaction card may be treated as another physical transaction card on the same transaction card account by the 20 issuer of the transaction card. To facilitate this, at step 330, when sending the card security credential to the mobile device 140, the issuer server 110 may also assign an additional sequence number to the transaction account for the transaction card that is being stored on mobile device 140. [61] Also, since the stored transaction card is not a physical plastic card, it may be 25 considered to be a virtual transaction card that is operable to provide the features of a plastic contactless transaction card. [62] After loading a transaction card account onto the mobile device 140, the mobile device 140 can be configured to be used in various scenarios when the physical plastic contactless card would otherwise be used. For example, the mobile 30 device 140 can be used for conducting mobile payment transactions. [63] Referring to Figure 7, shown there is an illustration of an example transaction card selection screen for a user interface 410 of an e-wallet application, after a transaction card has been loaded, as configured to be shown on display 230 of the -15- WO 2013/123577 PCT/CA2013/000151 mobile device 140. The e-wallet application may present a selection user interface 710 for selecting one of several transaction cards stored on the mobile device 140, for example, when the mobile device 140 is functioning as a contactless transaction card during a financial transaction. In such case, the user interface may display a 5 number of existing stored transaction cards (e.g., "Debit MasterCard® -5678" 712, "Coffee Shop Rewards Card -234" 714, "Supermarket Loyalty Card -76X" 716), as well as the newly added "ABC Bank Visa® -1213" card 718. As illustrated the example user interface shows the name of a name for the transaction card as well a number of trailing digits of a corresponding card number for the transaction card. 10 However, it will be understood that such identification is shown for illustration purposes only, and that other methods of presenting a transaction card selection screen may be possible. [64] If the mobile device 140 receives input selecting the "ABC Bank Visa@" card 718, the mobile device 140 may be configured to transmit the transaction card 15 information of the stored transaction card via the contactless transceiver 240 during a payment transaction. The mobile payment transactions may include transactions between the mobile device 140 and a point-of-sale (POS) terminal, and/or transactions between parties (peer-to-peer transactions). The peer-to-peer transactions may take place between two mobile devices 140a and 140b (as shown 20 in Figure 1), for example. [65] Certain peer-to-peer transactions, such as "I Owe You"s (IOUs), can be difficult to enforce due to their informal nature. IOUs are generally informal acknowledgements of a debt. Generally, no specific repayment terms are provided in an IOU other than an identity of a debtor and an amount owing. As well, it may 25 also be difficult to ensure the earliest possible repayment of the IOU because a party owing the IOU may not remember to repay the IOU even if that party has available funding and/or which IOU, if there are multiple IOUs outstanding, to repay first. [66] The repayment of IOUs can, thus, be automated so that repayment occurs immediately when repayment funds are available. An IOU may be created on a first 30 mobile device 140a associated with a first transaction account from which the amount owing is paid (an owing transaction account) and the IOU may then be sent to a second mobile device 140b associated with a second transaction account which is to receive the amount owing (a receiving transaction account). An association may -16- WO 2013/123577 PCT/CA2013/000151 then be established between the owing transaction account and the receiving transaction account such that whenever the owing transaction account receives any load amount (e.g., an amount intended by the user to be loaded onto the owing transaction account), that load amount is first used for repaying the amount owing 5 under the IOU. The various embodiments described below generally relate to a method of processing the amount owing from the owing transaction account to the receiving transaction account, including using the load amount to repay the amount owing. [67] For ease of exposition, reference is made simultaneously to Figures 8 to 12 10 for describing processing the amount owing from the owing transaction account to the receiving transaction account. [68] Referring now to Figure 8, shown therein is a flowchart diagram 800 illustrating the steps of processing repayment of an amount owing. [69] At step 810, the first mobile device 140a with a first memory 250 storing the 15 first transaction card 150a that corresponds to the first transaction account is provided. [70] At step 820, the second mobile device 140b with a second memory 250 storing the second transaction card 150b corresponding to the second transaction account is provided. 20 [71] As generally illustrated in Figure 1, each transaction account corresponding to the transaction cards 150a and 150b may be loaded onto the mobile devices 140a and 140b. For example, a transaction account can be loaded onto the memory 250 of each of the mobile devices 140a and 140b using the method described above or alternatively, through manual entry of the transaction card information. It will be 25 understood that each memory 250 may store multiple transaction accounts. As described above, the memory 250 may be housed in a secure element. [72] Referring now to Figure 9, therein illustrated a diagram 900 of a communication between two mobile devices 140a and 140b. [73] As described above, the first mobile device 140a may include the display 230 30 and may be configured to operate an e-wallet application. The e-wallet application may include an e-wallet user interface (UI) 410. Similarly, the second mobile device 140b also includes a display 230' and may also be configured to operate the e-wallet application. The e-wallet application stored on the memory 250 of the second mobile -17- WO 2013/123577 PCT/CA2013/000151 device 140b may also include an e-wallet UI 410'. It will be understood that the e wallet applications on each of the first and second mobile devices 140 and 140b may be the same or different types of e-wallet applications as long as each e-wallet application is compatible for communication with each other. 5 [74] As illustrated in Figure 9, the e-wallet UI 410 may provide a UI for creating an IOU 910 (an 'IOU creation UI'). It will be understood that the IOU creation UI 910 may be a separate software application from the e-wallet application. It will be further understood that the configuration of the illustrated IOU creation UI 910 is merely an example and that alternative configurations may similarly be used. 10 [75] The IOU creation UI 910 may include a field 912 for identifying each IOU (an 'IOU identifier (ID)') and various data fields for receiving information associated with the IOU. For example, this may include a field 712 for selecting an owing transaction account (an 'owing transaction account field'), a field 914 for identifying a party to receive the acknowledgement (a 'lender field'), a field 916 for identifying an amount 15 owing (an 'amount owing field'), and a field 918 for describing a context of the IOU (an 'IOU description field'). Furthermore, the IOU creation UI 910 may include a selection button 920 for confirming and submitting the IOU to be sent (an 'IOU submission button'). The IOU submission button 920 may also indicate a status of the delivery of the IOU. 20 [76] For ease of exposition and consistency, this example embodiment continues from the example described above with respect to Figures 4-7. In this example embodiment, the e-wallet UI 410 indicates that the e-wallet is associated with "John". From the IOU creation UI 910, the IOU ID 912 of the IOU being created is "IOU ID#130", the owing transaction account field 712 indicates that the user "John" has 25 selected to repay the amount owing 916 using the Debit MasterCard@ ending with the number "5678", the lender field 914 indicates that "Sam" is to receive the amount owing 916, the amount owing field 916 indicates that the amount owing is "$10", and the IOU description field 918 indicates that the amount owing 916 is for "John's share of dinner on Tues, Feb 14". Furthermore, the IOU submission button 920 30 indicates that John has submitted and sent the IOU. As illustrated in Figure 9, the IOU has been transmitted to the second mobile device 140b, via a communications 930. -18- WO 2013/123577 PCT/CA2013/000151 [77] As described above, each of the mobile devices 140a and 140b may include various communications modules 220 (as shown in Figure 2). In some embodiments, the IOU, or acknowledgement of an amount owing, may be transmitted from the mobile device 140a using its contactless transceiver 240. In 5 some embodiments, the IOU, or acknowledgement of an amount owing, may be received at the second mobile device 140b using its contactless transceiver 240. In some further embodiments, the contactless transceiver 240 in each of the first and second mobile devices 140a and 140b may be a NFC transceiver. [78] In some alternative embodiments, the mobile devices 140a and 140b may 10 transmit and receive, respectively, the repayment acknowledgment through any of the above described communication standards. [79] At step 830, the second mobile device 140b may receive, from the first mobile device 140a, the acknowledgement 930 acknowledging the amount owing. [80] Referring still to Figure 9, the e-wallet UI 410' on the second mobile device 15 140b indicates that the e-wallet application stored on the second mobile device 140b belongs to "Sam". On receipt of an IOU, the e-wallet Ul 410' may provide a display 950 for indicating to a user that an IOU has been received (a received IOU display). It will be understood that the received IOU display 950 may be a separate software application from the e-wallet UI 410'. It will be further understood that the 20 configuration of the illustrated received IOU display 950 is merely an example and that alternative configurations may similarly be used. [81] The received IOU display 950 may include several data fields describing the received IOU. These data fields may correspond to those provided in the IOU creation UI 910, such as the IOU ID 912', the amount owing field 916', and the IOU 25 description field 918'. Additionally, the received IOU display 950 may further include a field 952 identifying a party who sent the IOU (a 'borrower field'). [82] As illustrated in the received IOU display 950 in Figure 9, the IOU ID 912' of the received IOU is "ID#130", the amount owing field 916' indicates that the amount owing is "$10", and the IOU description field 918' indicates that the amount owing 30 916' is for John's "share of dinner on Tues, Feb 14". As shown in Figure 9, the data fields associated with the IOU created on John's e-wallet Ul 410 (IOU ID#130) corresponds with the IOU received by the second mobile device 140b, as shown on Sam's e-wallet Ul 410'. -19- WO 2013/123577 PCT/CA2013/000151 [83] After the acknowledgement is received by the second mobile device 140b, the second mobile device 140b may be prompted to provide the mobile device 140a with an account identifier corresponding to the receiving transaction account. The account identifier helps to establish an association between the receiving transaction 5 account and the owing transaction account 712 so that the repayment of the IOU from the owing transaction account 712 may be automated. [84] At step 840, the second mobile device 140b may transmit to the first mobile device 140a, the account identifier corresponding to the second transaction account. [85] In some embodiments, the account identifier may be associated with an 10 identifier corresponding to an electronic wallet account. For example, the account identifier transmitted by the second mobile device 140b to the first mobile device 140a may correspond to an identifier associated with Sam's electronic wallet account. As discussed above, the e-wallet identifiers may be stored on the e-wallet database 122 on the e-wallet server 120. 15 [86] As illustrated in Figure 9, the IOU creation UI 910 may include a status field 940 for indicating a status of receiving the account identifier (a 'status receiving field'), and the received IOU display 950 may further include a UI 960 for selecting an account for receiving the amount owing 916 (an 'account selecting UI'). In this example embodiment, the status receiving field 940 indicates that the first mobile 20 device 140a is currently awaiting receipt of the account identifier from the second mobile device 140b. [87] As illustrated in Figure 9, the account selecting UI 960 includes two transaction accounts 962 and 964 that may be selected for receiving the amount owing 916. It will be understood that fewer or more transaction accounts may be 25 provided in the account selecting UI 960. [88] In this example embodiment, the transaction account 962 associated with the "Debit Visa*" card ending in "2122" is selected. [89] In some embodiments, the receiving transaction account may be a default transaction account for receiving the amount owing 916. Therefore, the account 30 selecting UI 960 may not be provided. [90] As described above, each of the mobile devices 140a and 140b may include various communications modules. In some embodiments, the account identifier may be transmitted 930 from the second mobile device 140b using its contactless -20- WO 2013/123577 PCT/CA2013/000151 transceiver. In some embodiments, the account identifier may be received at the first mobile device 140a using its contactless transceiver. [91] In some alternative embodiments, the mobile devices 140a and 140b may transmit and receive, respectively, the account identifier through any of the above 5 described communication standards. [92] After the first mobile device 140a receives the account identifier from the second mobile device 140b, any amount that is intended to be loaded onto the owing transaction account 712 would first be used for repaying the amount owing 916 to the receiving transaction account 962 corresponding to the received account 10 identifier. [93] At step 850, the first mobile device 140a may receive a load amount to be loaded to the first transaction account 712, wherein, prior to adding the load amount to the first transaction account 712, the first mobile device 140a is configured to use the load amount to repay the amount owing 916 to the second transaction account 15 962. [94] Continuing with the example embodiment of Figure 9, but referring now to Figure 10, therein illustrated an example account balance 1010 after receiving the * load amount. [95] As illustrated in Figure 10, the account balance 1010 after receiving the load 20 amount may include the owing transaction account field 712, a field 1012 for indicating an account balance prior to receiving the load amount (a 'previous balance field') and a field 1014 for indicating an amount that was received for loading (a 'received load amount field'). [96] As described with reference to Figure 9, the owing transaction account field 25 712 is the "Debit MasterCard*" ending in "5678". As well, the received load amount field 1014 indicates that the owing transaction account 712 received the load amount of "$10", and the previous balance field 1012 indicates that the owing transaction account 712 had a balance of "$0" prior to receiving the load amount 1014. 30 [97] After the owing transaction account 712 receives the load amount 1014 of $10, the first mobile device 140a is configured to first process any IUs associated with the owing transaction account 712. As shown in Figure 10, a status field 1020 may be provided to show that the 1OUs associated with the owing transaction -21 - WO 2013/123577 PCT/CA2013/000151 account 712 is being processed (an IOU status field). In this example embodiment, the first mobile device 140a determines that the IOU ID#130 associated with the owing transaction account 712 is to be repaid with the received load amount 1014. [98] In some embodiments of processing a repayment of an amount owing 916, 5 the first mobile device 140a transmits a repayment message to the e-wallet server 120. As discussed above, the e-wallet server 120 may include an e-wallet database 122 for storing account identifiers and identifiers associated with transaction accounts corresponding to the account identifiers. The e-wallet database 122 may be further configured to store data identifying which of the transaction accounts is to 10 receive the amount owing 916. [99] The repayment message may include the received account identifier and the load amount 1014 for repaying the amount owing 916 to the receiving transaction account 962. Using the repayment message, the e-wallet server 120 may be configured to identify the receiving transaction account 962 that corresponds to the 15 received account identifier. After having identified the receiving transaction account, the e-wallet server 120 may add the load amount 1014 to the identified receiving transaction account 962 by, for example, communicating with an issuer server 110 for the receiving transaction account 962. [100] In some embodiments, if the load amount 1014 is greater than the amount 20 owing 916, the portion of the load amount 1014 that remains after paying the amount owing 916 is added to the first transaction account 712. In some alternate embodiments, if the load amount 1014 is less than the amount owing 916, the amount owing 916 is reduced by the load amount 1014. [101] In some embodiments, multiple amounts owing 916 under multiple IOUs may 25 be associated with an owing transaction account 712 and the multiple amounts owing 916 may form a payment queue. The payment queue may be stored on a memory of the mobile device associated with the owing transaction account 712, as will be described below. [102] Referring now to Figure 11, therein illustrated an example payment received 30 notification 1110. [103] Continuing the example from Figure 10, after the first mobile device 140a processes the amount owing 916 under IOU "ID#130", the second mobile device 140b that is associated with the receiving transaction account 962 may receive a -22- WO 2013/123577 PCT/CA2013/000151 payment received notification 1110 for indicating that IOU "ID#130" has been repaid. Correspondingly, the account balance 1010 associated with the owing transaction account 712 may be updated and again provided to the first mobile device 140a. [104] Referring to Figure 12, therein illustrated the example account balance 1010' 5 of the owing transaction account 712 after the amount owing 916 is repaid. As illustrated in the updated IOU status field 1020', the IOU "ID#130" has been repaid using the owing transaction account 712. Accordingly, a field 1212 showing a current balance of the owing transaction account 712 indicates that there is "$0" remaining since the received load amount 1014 (shown in Figure 10) has been repaid to the 10 receiving transaction account 962. [105] Referring now to Figure 13, shown there is a screenshot of an example payment queue 1310. As described briefly above, the owing transaction account 712 may be associated with multiple amounts owing 916 under multiple 1OUs. In some embodiments, the multiple amounts owing 916 may form a payment queue 1310. As 15 illustrated in Figure 13, the example payment queue 1310 includes three different amounts owing 1320, 1322 and 1324 that are each associated with a different IOU ID 912 and a different lender 914. It will be understood one or more of the lender fields 914 in the payment queue 1310 may include the same lender. [106] The payment queue can be considered a queue because load amounts may 20 go towards paying off IOUs in the order in which the lenders are presented in the queue. For example, the amount of "$10" illustrated in Figure 10 was directed towards paying off "Sam" before paying off "Tom" or "Victor" because the "IOU ID" for "Sam" was in the first position in the queue. [107] In addition to the payment queue 1310, an UI 1350 for editing the payment 25 queue (an 'IOU editing UI') may be provided. For example, a selection button 1352 may be provided for adding an IOU to the payment queue 1310 (an 'add IOU button') and another selection button 1354 may be provided for modifying an existing IOU (a 'modify IOU button'). When the add IOU button 1352 is selected, the mobile device 140 may receive a signal indicating that a new IOU is to be created 30 and the mobile device 140 may be configured to provide the IOU creation UI 910, as described above, so that the new IOU can be created. Similarly, when the modify IOU button 1354 is selected, the mobile device 140 may receive a signal indicating that one or more of the existing IOUs 1320, 1322 and 1324 is to be modified, and -23- WO 2013/123577 PCT/CA2013/000151 the mobile device 140 may be configured for providing any such modifications. Example modifications include the order in which the existing IUs 1320, 1322 and 1324 are repaid (i.e., the positions that each IOU may be placed in the payment queue). In another example, any of the amounts owing field 916 and the lender field 5 914 may be modified. [108] It will be understood that the functionalities provided by the selection buttons 1352 and 1354 are merely examples and that other functionalities associated with the payment queue may be provided. [109] Referring now to Figure 14, therein illustrated an example UI 1410 for 10 selecting options associated with the amount owing 916 at a second mobile device 140b. [110] As described above with reference to Figure 9, the second mobile device 140b may provide the account selecting UI 960 for receiving data indicating which receiving transaction account 962 is selected for receiving the amount owing 916. In 15 various embodiments, the second mobile device 140b may be further configured to provide an UI 1410 for selecting multiple options associated with an IOU. [111] In the example embodiment of Figure 14, three different selection buttons 1412, 1414 and 1416 are provided. It will be understood that fewer or more selection buttons may be provided. It will be further understood that other Ul configurations 20 may be used. [112] A first selection button 1412 may provide for modifying of a repayment account (a modify repayment account button), a second selection button 1414 may provide for an IOU to be forgiven (an IOU forgiving button), and a third selection button 1416 may provide for sending of a reminder of the IOU to the owing party (a 25 reminder button). [113] When the modify repayment account button 1412 is selected, the second mobile device 140b may receive a signal indicating that the selected receiving transaction account 962 is to be edited and/or changed. The second mobile device 140b may be configured to provide the account selecting UI 960 again, or a variation 30 of the account selecting UI 960 may be provided to allow the changing of the receiving transaction account for the indicated IOU. [114] When the IOU forgiving button 1414 is selected, the second mobile device 140b receives a data signal indicating that IOU #130 is to be cancelled. The second -24 - WO 2013/123577 PCT/CA2013/000151 mobile device 140b may be configured to delete IOU #130. This may also involve the second mobile device 140b communicating with the e-wallet server 120 to indicate to the IOU has been forgiven. The e-wallet server 120 may, in turn, relay this message to the first mobile device 140a so that the e-wallet application stored 5 on the first mobile device 140a may update the various statuses of the 1OUs stored in its payment queue. Additionally or alternatively, such communication indicating the IOU has been forgiven may sent directly from the second mobile device 140b to the first mobile device 140a. [115] When the reminder button 1416 is selected, the second mobile device 140b 10 receives a data signal indicating that a reminder message is to be sent to the first mobile device 140a to remind the first mobile device 140a of IOU #130. [116] The present invention has been described here by way of example only. Various modification and variations may be made to these exemplary embodiments without departing from the spirit and scope of the invention, which is limited only by 15 the appended claims. [117] For example, the steps of a method in accordance with any of the embodiments described herein may be performed in any order, whether or not such steps are described in the claims, figures or otherwise in any sequential numbered or lettered manner. Also, in the various user interfaces illustrated in the figures, it 20 will be understood that the illustrated user interface text and controls are provided as examples only and are not meant to be limiting. Other suitable user interface elements may be possible. - 25 -

权利要求:
Claims (34)
[1] 1. A method of loading a transaction card account onto a mobile device, the mobile device comprising a memory and a contactless reader, the method 5 comprising: - reading, via the contactless reader, transaction card information from a physical contactless transaction card corresponding to the transaction card account; - sending a retrieval message, to an issuer server, to retrieve a card 10 security credential for the transaction card account, the retrieval message comprising the transaction card information for identifying the transaction card account at the issuer server; - receiving, from the issuer server, a card security credential for the transaction card account; and 15 - storing, - the transaction card information, and - the card security credential; as a transaction card corresponding to the transaction account, on the memory of the mobile device. 20
[2] 2. The method of claim 1, wherein the mobile device comprises a secure element, and the memory is housed in the secure element.
[3] 3. The method of claim 1 or claim 2, wherein the contactless reader comprises a 25 Near Field Communications (NFC) integrated circuit (IC).
[4] 4. The method of any one of claims 1 to 3, further comprising: - displaying a user interface on the mobile device to receive a security input for verification against the card security credential; and 30 - verifying the security input against the card security credential.
[5] 5. The method of claim 4, wherein, prior to the storing, the displaying and verifying is performed to authenticate the owner of the transaction account. - 26 - WO 2013/123577 PCT/CA2013/000151
[6] 6. The method of claim 4 or claim 5, wherein the security input comprises an inputted Personal Identification Number (PIN) and the card security credential comprises an encrypted PIN, and wherein, the verifying comprises determining 5 whether the inputted PIN matches the encrypted PIN.
[7] 7. The method of any one of claims 1 to 6, wherein the mobile device comprises a contactless transmitter, and the mobile device is configured to transmit the transaction card information of the stored transaction card via the contactless 10 transmitter during a payment transaction.
[8] 8. The method of claim 7, wherein the mobile device comprises a contactless transceiver that comprises the contactless reader and the contactless transmitter. 15
[9] 9. A system for loading a transaction card account, the system comprising, - a mobile device comprising a processor, a contactless reader operatively coupled to the processor, and a memory storing a plurality of instructions, which when executed by the processor causes the processor to: 20 - read, via the contactless reader, transaction card information from a physical contactless transaction card corresponding to the transaction card account; - send a retrieval message, to an issuer server, to retrieve a card security credential for the transaction card account, the retrieval 25 message comprising the transaction card information for identifying the transaction card account at the issuer server; - receive, from the issuer server, a card security credential for the transaction card account; and - store, 30 - the transaction card information, and - the card security credential; as a transaction card corresponding to the transaction account, on the memory of the mobile device. - 27 - WO 2013/123577 PCT/CA2013/000151
[10] 10. The system of claim 9, wherein the mobile device comprises a secure element, and the memory is housed in the secure element. 5
[11] 11. The system of claim 9 or claim 10, wherein the contactless reader comprises a Near Field Communications (NFC) integrated circuit (IC).
[12] 12. The system of any one of claims 9 to 11, further comprising: - displaying a user interface on the mobile device to receive a security 10 input for verification against the card security credential; and - verifying the security input against the card security credential.
[13] 13. The system of claim 12, wherein, prior to the storing, the displaying and verifying is performed to authenticate the owner of the transaction account. 15
[14] 14. The system of claim 12 or claim 13, wherein the security input comprises an inputted Personal Identification Number (PIN) and the card security credential comprises an encrypted PIN, and wherein, the verifying comprises determining whether the inputted PIN matches the encrypted PIN. 20
[15] 15. The system of any one of claims 9 to 14, wherein the mobile device comprises a contactless transmitter, and the mobile device is configured to transmit the transaction card information of the stored transaction card via the contactless transmitter during a payment transaction. 25
[16] 16. The system of claim 15, wherein the mobile device comprises a contactless transceiver that comprises the contactless reader and the contactless transmitter.
[17] 17. A method of processing an amount owing from a first transaction account to a 30 second transaction account, the method comprising: - providing a first mobile device comprising a first memory storing a first transaction card corresponding to the first transaction account; - 28 - WO 2013/123577 PCT/CA2013/000151 - providing a second mobile device comprising a second memory storing a second transaction card corresponding to the second transaction account; - receiving at the second mobile device, from the first mobile device, an 5 acknowledgement that acknowledges the amount owing; - transmitting, from the second mobile device to the first mobile device, an account identifier corresponding to the second transaction account; and - receiving, at the first mobile device, a load amount to be loaded to the 10 first transaction account, wherein, prior to adding the load amount to the first transaction account, the first mobile device is configured to use the load amount to repay the amount owing to the second transaction account. 15
[18] 18. The method of claim 17, further comprising: - transmitting, from the first mobile device to an e-wallet server, a repayment message comprising: - the received account identifier corresponding to the second transaction account, and 20 - the load amount for repaying the amount owing to the second transaction account; - wherein the e-wallet server is configured to identify the second transaction account from the received account identifier and add the load amount to the second transaction account. 25
[19] 19. The method of claim 17 or claim 18, wherein the load amount is greater than the amount owing, and a remaining amount of the load amount not used to repay the amount owing is added to the first transaction account. 30
[20] 20. The method of claim 17 or claim 18, wherein the load amount is less than the amount owing, and the amount owing is reduced by the load amount.
[21] 21. The method of any one of claims 17 to 20, further comprising: - 29 - WO 2013/123577 PCT/CA2013/000151 - storing, on the first memory, a payment queue associated with the first transaction account, wherein the payment queue comprises a plurality of amounts owing from the first transaction account. 5
[22] 22. The method of any one of claims 17 to 21, wherein the first mobile device comprises a first contactless transceiver, and wherein the acknowledgment is transmitted, and the account identifier is received, via the first contactless transceiver. 10
[23] 23. The method of claim 22, wherein the first contactless transceiver comprises a Near Field Communications (NFC) integrated circuit (IC).
[24] 24. The method of any one of claims 17 to 23, wherein the second mobile device comprises a second contactless transceiver, and wherein the acknowledgement is 15 received, and the account identifier is transmitted, via the second contactless transceiver.
[25] 25. The method of claim 24, wherein the second contactless transceiver comprises a Near Field Communications (NFC) integrated circuit (IC). 20
[26] 26. A system for processing an amount owing from a first transaction account to a second transaction account, the system comprising: - a first mobile device comprising a first processor and a first memory storing a first transaction card corresponding to the first transaction 25 account; - a second mobile device comprising a second processor and a second memory storing a second transaction card corresponding to the second transaction account, wherein the second processor is configured to: 30 - receive, from the first mobile device, an acknowledgement that acknowledges the amount owing; and - transmit, to the first mobile device, an account identifier corresponding to the second transaction account; and - 30 - WO 2013/123577 PCT/CA2013/000151 - wherein, the first mobile device configured to: - receive a load amount to be loaded to the first transaction account, and, prior to adding the load amount to the first transaction account, the first mobile device is configured to use 5 the load amount to repay the amount owing to the second transaction account.
[27] 27. The system of claim 26, wherein the first mobile device is further configured to: 10 - transmit to an e-wallet server, a repayment message comprising - the received account identifier corresponding to the second transaction account, and - the load amount for repaying the amount owing to the second transaction account; 15 - wherein the e-wallet server is configured to identify the second transaction account from the received account identifier and add the load amount to the second transaction account.
[28] 28. The system of claim 26 or claim 27, wherein the load amount is greater than 20 the amount owing, and a remaining amount of the load amount not used to repay the amount owing is added to the first transaction account.
[29] 29. The system of claim 26 or claim 27, wherein the load amount is less than the amount owing, and the amount owing is reduced by the load amount. 25
[30] 30. The system of any one of claims 26 to 29, wherein the first mobile device is further configured to: - store, on the first memory, a payment queue associated with the first transaction account, wherein the payment queue comprises a plurality 30 of amounts owing from the first transaction account.
[31] 31. The system of any one of claims 26 to 30, wherein the first mobile device comprises a first contactless transceiver, and wherein the acknowledgment is - 31 - WO 2013/123577 PCT/CA2013/000151 transmitted, and the account identifier is received, via the first contactless transceiver.
[32] 32. The system of claim 31, wherein the first contactless transceiver comprises a 5 Near Field Communications (NFC) integrated circuit (IC).
[33] 33. The system of any one of claims 26 to 32, wherein the second mobile device comprises a second contactless transceiver, and wherein the acknowledgement is received, and the account identifier is transmitted, via the second contactless 10 transceiver.
[34] 34. The system of claim 33, wherein the second contactless transceiver comprises a Near Field Communications (NFC) integrated circuit (IC). - 32 -

类似技术:

公开号 | 公开日 | 专利标题

US10776776B2|2020-09-15|System and method of loading a transaction card and processing repayment on a mobile device

US11057229B2|2021-07-06|Mobile payment application architecture

US20210256507A1|2021-08-19|System and method for processing payment during an electronic commerce transaction

US10546290B2|2020-01-28|Methods, systems, and computer readable media for provisioning and utilizing an aggregated soft card on a mobile device

US10922675B2|2021-02-16|Remote transaction system, method and point of sale terminal

CA2859526A1|2013-06-27|System and method for dynamic temporary payment authorization in a portable communication device

WO2012174071A2|2012-12-20|System and method of multi-factor balance inquiry and electronic funds transfer

AU2020260506A1|2020-11-26|Remote transaction system, method and point of sale terminal

US20210004806A1|2021-01-07|Transaction Device Management

EP3340144A1|2018-06-27|Electronic payment device transactions

同族专利:

公开号 | 公开日

US10776776B2|2020-09-15|

US20140252087A1|2014-09-11|

US8763896B2|2014-07-01|

EP2817772A1|2014-12-31|

CA2965398C|2020-07-28|

CA2837491C|2017-07-18|

US9349125B2|2016-05-24|

US20160239828A1|2016-08-18|

US10269007B2|2019-04-23|

US20200058017A1|2020-02-20|

WO2013123577A1|2013-08-29|

US20130221092A1|2013-08-29|

CA2837491A1|2013-08-29|

CA2965398A1|2013-08-29|

EP2817772A4|2015-10-07|

引用文献:

公开号 | 申请日 | 公开日 | 申请人 | 专利标题

EP1107196B1|1998-08-07|2007-03-21|Ali Hassan Al-Khaja|A wireless electronic system for performing transactions|

US20020038287A1|2000-08-30|2002-03-28|Jean-Marc Villaret|EMV card-based identification, authentication, and access control for remote access|

US7693783B2|2002-06-12|2010-04-06|Cardinalcommerce Corporation|Universal merchant platform for payment authentication|

US20040127256A1|2002-07-30|2004-07-01|Scott Goldthwaite|Mobile device equipped with a contactless smart card reader/writer|

JP2003099695A|2002-08-01|2003-04-04|Hitachi Ltd|Electronic wallet loan system|

US6776339B2|2002-09-27|2004-08-17|Nokia Corporation|Wireless communication device providing a contactless interface for a smart card reader|

US8700729B2|2005-01-21|2014-04-15|Robin Dua|Method and apparatus for managing credentials through a wireless network|

US7997476B2|2005-09-15|2011-08-16|Capital One Financial Corporation|Wireless devices for storing a financial account card and methods for storing card data in a wireless device|

GB2444798B|2006-12-15|2010-06-30|Innovision Res & Tech Plc|Communications devices comprising near field RF communicators|

CA2647636A1|2006-03-30|2008-03-06|Obopay Inc.|Mobile person-to-person payment system|

US8793184B2|2007-02-12|2014-07-29|Visa U.S.A. Inc.|Mobile payment services|

US20080208743A1|2007-02-22|2008-08-28|First Data Corporation|Transfer of value between mobile devices in a mobile commerce system|

EP2056246A1|2007-10-30|2009-05-06|Nederlandse Organisatie voor toegepast-natuurwetenschappelijk Onderzoek TNO|Electronic payments using payment cards|

US8083140B1|2008-02-05|2011-12-27|Sprint Communications Company L.P.|System and method of over-the-air provisioning|

US9947002B2|2008-02-15|2018-04-17|First Data Corporation|Secure authorization of contactless transaction|

US9454865B2|2008-08-06|2016-09-27|Intel Corporation|Methods and systems to securely load / reload acontactless payment device|

US8127999B2|2008-08-14|2012-03-06|Visa U.S.A. Inc.|Wireless mobile communicator for contactless payment on account read from removable card|

SK50862008A3|2008-09-19|2010-06-07|Logomotion, S. R. O.|System for electronic payment applications and method for payment authorization|

WO2010114499A2|2009-03-17|2010-10-07|Guelseven Salih|Mobile payment device|

US9135424B2|2009-05-29|2015-09-15|Paypal, Inc.|Secure identity binding |

US9224146B2|2009-09-30|2015-12-29|The Toronto Dominion Bank|Apparatus and method for point of sale terminal fraud detection|

US9129270B2|2010-03-02|2015-09-08|Gonow Technologies, Llc|Portable E-wallet and universal card|

EP2490168A1|2011-02-14|2012-08-22|Research In Motion Limited|Message based procurement|

US20120290449A1|2011-05-10|2012-11-15|Mullen Jeffrey D|Systems and methods for a mobile electronic wallet|

US9792593B2|2011-11-23|2017-10-17|The Toronto-Dominion Bank|System and method for processing an online transaction request|

US8763896B2|2012-02-23|2014-07-01|XRomb Inc.|System and method of loading a transaction card and processing repayment on a mobile device|US9047601B2|2006-09-24|2015-06-02|RFCyber Corpration|Method and apparatus for settling payments using mobile devices|

EP2731037B1|2007-09-24|2019-08-07|Apple Inc.|Embedded authentication systems in an electronic device|

US9374710B2|2010-08-16|2016-06-21|Telefonaktiebolaget Lm Ericsson |Mediation server, control method therefor, communication device, control method therefor, communication system, and computer program|

US20120290449A1|2011-05-10|2012-11-15|Mullen Jeffrey D|Systems and methods for a mobile electronic wallet|

US8769624B2|2011-09-29|2014-07-01|Apple Inc.|Access control utilizing indirect authentication|

US9002322B2|2011-09-29|2015-04-07|Apple Inc.|Authentication with secondary approver|

US10991015B2|2012-01-10|2021-04-27|Change Up Inc.|Consumer controlled portfolio charitable giving system|

EP2626824A1|2012-02-09|2013-08-14|Deutsche Telekom AG|Management of virtual wallets provided by means of a mobile terminal|

US8763896B2|2012-02-23|2014-07-01|XRomb Inc.|System and method of loading a transaction card and processing repayment on a mobile device|

US20140006276A1|2012-06-28|2014-01-02|Bank Of America Corporation|Mobile wallet account number differentiation|

US9585006B2|2013-06-26|2017-02-28|Cellco Partnership|Express mobile device access provisioning methods, systems, and apparatus|

US9898642B2|2013-09-09|2018-02-20|Apple Inc.|Device, method, and graphical user interface for manipulating user interfaces based on fingerprint sensor inputs|

KR101952928B1|2013-10-30|2019-02-27|애플 인크.|Displaying relevant user interface objects|

US20150149291A1|2013-11-26|2015-05-28|Najla Ferraz Abdala|Magnetic card transaction system based in cloud computing and simulated magnetic cards|

WO2015107346A1|2014-01-15|2015-07-23|Iaxept Limited|Authentication method and system|

US10482461B2|2014-05-29|2019-11-19|Apple Inc.|User interface for payments|

US9967401B2|2014-05-30|2018-05-08|Apple Inc.|User interface for phone call routing among devices|

US10339293B2|2014-08-15|2019-07-02|Apple Inc.|Authenticated device used to unlock another device|

US9547419B2|2014-09-02|2017-01-17|Apple Inc.|Reduced size configuration interface|

US10066959B2|2014-09-02|2018-09-04|Apple Inc.|User interactions for a mapping application|

FR3031613B1|2015-01-09|2018-04-06|Ingenico Group|METHOD FOR PROCESSING A TRANSACTION FROM A COMMUNICATION TERMINAL|

US20160224973A1|2015-02-01|2016-08-04|Apple Inc.|User interface for payments|

US9574896B2|2015-02-13|2017-02-21|Apple Inc.|Navigation user interface|

US10254911B2|2015-03-08|2019-04-09|Apple Inc.|Device configuration user interface|

US11037139B1|2015-03-19|2021-06-15|Wells Fargo Bank, N.A.|Systems and methods for smart card mobile device authentication|

US11188919B1|2015-03-27|2021-11-30|Wells Fargo Bank, N.A.|Systems and methods for contactless smart card authentication|

US20160358133A1|2015-06-05|2016-12-08|Apple Inc.|User interface for loyalty accounts and private label accounts for a wearable device|

US9940637B2|2015-06-05|2018-04-10|Apple Inc.|User interface for loyalty accounts and private label accounts|

US10387846B2|2015-07-10|2019-08-20|Bank Of America Corporation|System for affecting appointment calendaring on a mobile device based on dependencies|

US10387845B2|2015-07-10|2019-08-20|Bank Of America Corporation|System for facilitating appointment calendaring based on perceived customer requirements|

CN105654376B|2015-12-30|2020-03-13|中国建设银行股份有限公司|Cardless withdrawal method, related device and system|

CN105654377B|2015-12-30|2020-01-17|中国建设银行股份有限公司|Cardless withdrawal method, related device and system|

CN105488922A|2015-12-30|2016-04-13|中国建设银行股份有限公司|Cardless money withdrawing method and related devices and systems|

KR20170084783A|2016-01-13|2017-07-21|삼성전자주식회사|Payment processing method and electronic device supporting the same|

US10628821B2|2016-01-26|2020-04-21|American Greetings|Activation and assigning value to gift cards using RFID|

US11113688B1|2016-04-22|2021-09-07|Wells Fargo Bank, N.A.|Systems and methods for mobile wallet provisioning|

DK179186B1|2016-05-19|2018-01-15|Apple Inc|REMOTE AUTHORIZATION TO CONTINUE WITH AN ACTION|

US10621581B2|2016-06-11|2020-04-14|Apple Inc.|User interface for transactions|

DK201670622A1|2016-06-12|2018-02-12|Apple Inc|User interfaces for transactions|

US10949838B1|2016-08-23|2021-03-16|Wells Fargo Bank, N.A.|Mobile wallet registration via ATM|

US9842330B1|2016-09-06|2017-12-12|Apple Inc.|User interfaces for stored-value accounts|

US10860199B2|2016-09-23|2020-12-08|Apple Inc.|Dynamically adjusting touch hysteresis based on contextual data|

US10496808B2|2016-10-25|2019-12-03|Apple Inc.|User interface for managing access to credentials for use in an operation|

CN108604345B|2017-01-25|2020-09-25|华为技术有限公司|Method and device for adding bank card|

KR20200096696A|2017-09-09|2020-08-12|애플 인크.|Implementation of biometric authentication|

KR102185854B1|2017-09-09|2020-12-02|애플 인크.|Implementation of biometric authentication|

CN109842605B|2017-11-29|2020-07-07|华为技术有限公司|Card binding method and terminal|

US11170085B2|2018-06-03|2021-11-09|Apple Inc.|Implementation of biometric authentication|

US11100349B2|2018-09-28|2021-08-24|Apple Inc.|Audio assisted enrollment|

US10860096B2|2018-09-28|2020-12-08|Apple Inc.|Device control using gaze information|

WO2020123274A1|2018-12-10|2020-06-18|Mastercard International Incorporated|Systems and methods for provisioning accounts|

US20200302517A1|2019-03-24|2020-09-24|Apple Inc.|User interfaces for managing an account|

EP3719730A1|2019-04-03|2020-10-07|Nxp B.V.|Method for providing a digital representation of a transaction card in a mobile device|

US11169830B2|2019-09-29|2021-11-09|Apple Inc.|Account management user interfaces|

法律状态:
2017-01-19| MK1| Application lapsed section 142(2)(a) - no request for examination in relevant period|

优先权:

申请号 | 申请日 | 专利标题

US201261602421P| true| 2012-02-23|2012-02-23||

US61/602,421||2012-02-23||

US13/464,484||2012-05-04||

US13/464,484|US8763896B2|2012-02-23|2012-05-04|System and method of loading a transaction card and processing repayment on a mobile device|

PCT/CA2013/000151|WO2013123577A1|2012-02-23|2013-02-22|System and method of loading a transaction card and processing repayment on a mobile device|

[返回顶部]